{
  "version": "public-reference-2026-09-08.1",
  "synthetic": true,
  "design": {
    "version": "2026-09-08.1",
    "created_at_utc": "2026-09-08T17:05:09.338823+00:00",
    "origin": "Newly authored synthetic full-scope reference design; not historical cases or customer tasks.",
    "process": "Written handoff of a fictional document package and proposed external distribution decision.",
    "base_tasks": [
      {
        "base_task_id": "J1",
        "newly_authored_focus": "A release is explicitly withdrawn",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J1-A",
            "kind": "new_application",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J1"
          },
          {
            "id": "J1-B",
            "kind": "correction_or_exception",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              },
              {
                "id": "E2",
                "time": "10:00",
                "role": "R-A",
                "action": "withdraw",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J1"
          }
        ]
      },
      {
        "base_task_id": "J2",
        "newly_authored_focus": "Approval is bound to the current revision",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J2-A",
            "kind": "new_application",
            "current_revision": 3,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 3,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J2"
          },
          {
            "id": "J2-B",
            "kind": "correction_or_exception",
            "current_revision": 4,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 3,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J2"
          }
        ]
      },
      {
        "base_task_id": "J3",
        "newly_authored_focus": "Approval is bound to the permitted audience",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J3-A",
            "kind": "new_application",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J3"
          },
          {
            "id": "J3-B",
            "kind": "correction_or_exception",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "internal"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J3"
          }
        ]
      },
      {
        "base_task_id": "J4",
        "newly_authored_focus": "An unlisted role cannot withdraw the valid approval",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J4-A",
            "kind": "new_application",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J4"
          },
          {
            "id": "J4-B",
            "kind": "correction_or_exception",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              },
              {
                "id": "E2",
                "time": "10:00",
                "role": "R-X",
                "action": "withdraw",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J4"
          }
        ]
      },
      {
        "base_task_id": "J5",
        "newly_authored_focus": "A required missing file prevents release despite approval",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J5-A",
            "kind": "new_application",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J5"
          },
          {
            "id": "J5-B",
            "kind": "correction_or_exception",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": false,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J5"
          }
        ]
      },
      {
        "base_task_id": "J6",
        "newly_authored_focus": "Conflicting equally authorized roles require clarification",
        "base_order": "Assess the next permitted external distribution step for this fictional document package under its supplied approval record.",
        "facts": [
          {
            "id": "R1",
            "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
          },
          {
            "id": "R2",
            "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
          },
          {
            "id": "R3",
            "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
          },
          {
            "id": "R4",
            "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
          },
          {
            "id": "R5",
            "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
          },
          {
            "id": "R6",
            "text": "Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
          }
        ],
        "glossary": "Glossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.",
        "structured": {
          "format": "structured-fact-list-v1",
          "facts": [
            {
              "id": "R1",
              "text": "Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval."
            },
            {
              "id": "R2",
              "text": "External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request."
            },
            {
              "id": "R3",
              "text": "For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution."
            },
            {
              "id": "R4",
              "text": "An event from a role not named as authorized does not alter an authorized role approval or withdrawal."
            },
            {
              "id": "R5",
              "text": "Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together."
            },
            {
              "id": "R6",
              "text": "Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted."
            }
          ]
        },
        "variants": [
          {
            "id": "J6-A",
            "kind": "new_application",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              },
              {
                "id": "E2",
                "time": "09:00",
                "role": "R-B",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J6"
          },
          {
            "id": "J6-B",
            "kind": "correction_or_exception",
            "current_revision": 2,
            "requested_audience": "external",
            "required_package_complete": true,
            "events": [
              {
                "id": "E1",
                "time": "09:00",
                "role": "R-A",
                "action": "approve",
                "revision": 2,
                "audience": "external"
              },
              {
                "id": "E2",
                "time": "09:00",
                "role": "R-B",
                "action": "withdraw",
                "revision": 2,
                "audience": "external"
              }
            ],
            "question": "May this current revision be distributed externally now? State the next permitted action and any required clarification.",
            "document_id": "DOC-J6"
          }
        ]
      }
    ],
    "conditions": [
      "glossary",
      "structured"
    ],
    "information_equality": "Identical ordered rule IDs and exact fact texts per base task. Only plain-text list versus JSON fact-list representation changes. Case, question and response instruction identical across conditions. Length is recorded and differs because JSON adds syntax.",
    "unknown_variant_limit": "Each call gets one previously unseen case within a fresh conversation. Training-data novelty cannot be established.",
    "execution": "24 independent fresh contexts; fixed model/configuration; one response per condition and variant; no retries or fallback; no real distribution.",
    "evaluation": "Four separate dimensions: task action, scope constraints, correction/event handling, appropriate clarification. Exact field matches and evidence IDs against the frozen reference; explanation separately reviewed. Missing or incomplete outputs stay missing. No advantage required.",
    "blinding": "After collection, assign fixed shuffled anonymous IDs to answers; assess explanations without condition labels where possible. Recognizable formatting and one agent knowing the design limit masking.",
    "external_dependency_for_reference": null,
    "customer_contract_limit": "Customer-specific pilot still requires six authorized customer orders and the named customer recipient environment."
  },
  "submitted_input_texts": [
    {
      "case_id": "J1-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J1-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J1\"\n}"
    },
    {
      "case_id": "J1-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J1-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J1\"\n}"
    },
    {
      "case_id": "J1-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J1-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"10:00\",\n      \"role\": \"R-A\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J1\"\n}"
    },
    {
      "case_id": "J1-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J1. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J1-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"10:00\",\n      \"role\": \"R-A\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J1\"\n}"
    },
    {
      "case_id": "J2-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J2-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 3,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 3,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J2\"\n}"
    },
    {
      "case_id": "J2-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J2-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 3,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 3,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J2\"\n}"
    },
    {
      "case_id": "J2-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J2-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 4,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 3,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J2\"\n}"
    },
    {
      "case_id": "J2-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J2. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J2-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 4,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 3,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J2\"\n}"
    },
    {
      "case_id": "J3-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J3-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J3\"\n}"
    },
    {
      "case_id": "J3-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J3-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J3\"\n}"
    },
    {
      "case_id": "J3-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J3-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"internal\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J3\"\n}"
    },
    {
      "case_id": "J3-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J3. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J3-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"internal\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J3\"\n}"
    },
    {
      "case_id": "J4-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J4-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J4\"\n}"
    },
    {
      "case_id": "J4-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J4-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J4\"\n}"
    },
    {
      "case_id": "J4-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J4-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"10:00\",\n      \"role\": \"R-X\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J4\"\n}"
    },
    {
      "case_id": "J4-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J4. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J4-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"10:00\",\n      \"role\": \"R-X\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J4\"\n}"
    },
    {
      "case_id": "J5-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J5-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J5\"\n}"
    },
    {
      "case_id": "J5-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J5-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J5\"\n}"
    },
    {
      "case_id": "J5-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J5-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": false,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J5\"\n}"
    },
    {
      "case_id": "J5-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J5. Authorized roles with equal priority: R-A. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J5-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": false,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J5\"\n}"
    },
    {
      "case_id": "J6-A",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J6-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"09:00\",\n      \"role\": \"R-B\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J6\"\n}"
    },
    {
      "case_id": "J6-A",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J6-A\",\n  \"kind\": \"new_application\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"09:00\",\n      \"role\": \"R-B\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J6\"\n}"
    },
    {
      "case_id": "J6-B",
      "condition": "glossary",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\nGlossary\n- R1: Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\n- R2: External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\n- R3: For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\n- R4: An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\n- R5: Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\n- R6: Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\n\nCASE\n{\n  \"id\": \"J6-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"09:00\",\n      \"role\": \"R-B\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J6\"\n}"
    },
    {
      "case_id": "J6-B",
      "condition": "structured",
      "prompt": "SYNTHETIC REFERENCE TASK. Use only the handoff and case. This is a proposed action; do not distribute or approve anything. Return one JSON object with action (release_allowed or hold), external_distribution_allowed (boolean), active_event_ids (array of relevant authorized event IDs; preserve conflicting records), clarification (none, request_current_approval, request_external_approval, complete_package, or clarify_conflicting_authority), evidence (array of supplied rule/event IDs), and a short explanation. Historical approvals for a different revision or audience are not active approvals of this request.\n\nHANDOFF\n{\n  \"format\": \"structured-fact-list-v1\",\n  \"facts\": [\n    {\n      \"id\": \"R1\",\n      \"text\": \"Complete means all required package files are present and match the chosen manifest. Completeness is necessary for external distribution but does not itself grant approval.\"\n    },\n    {\n      \"id\": \"R2\",\n      \"text\": \"External distribution requires an explicit approval from a named authorized role for the current document revision and the external audience. Approval of another revision or only an internal audience does not extend to this request.\"\n    },\n    {\n      \"id\": \"R3\",\n      \"text\": \"For the same document and authorized role, a later explicit withdrawal supersedes its earlier approval. A withdrawn approval requires a new approval for the current revision before external distribution.\"\n    },\n    {\n      \"id\": \"R4\",\n      \"text\": \"An event from a role not named as authorized does not alter an authorized role approval or withdrawal.\"\n    },\n    {\n      \"id\": \"R5\",\n      \"text\": \"Unresolved disagreement between equally authorized roles requires a hold and clarification. Neither event order nor an unsupported authority assumption settles such a conflict. If equally authorized roles agree, their records are retained together.\"\n    },\n    {\n      \"id\": \"R6\",\n      \"text\": \"Scope: fictional document DOC-J6. Authorized roles with equal priority: R-A, R-B. Current revision, intended audience and required-package completeness are exactly the values in the case. Event times are fictional, within this one case; no real dates or responsibilities are asserted.\"\n    }\n  ]\n}\n\nCASE\n{\n  \"id\": \"J6-B\",\n  \"kind\": \"correction_or_exception\",\n  \"current_revision\": 2,\n  \"requested_audience\": \"external\",\n  \"required_package_complete\": true,\n  \"events\": [\n    {\n      \"id\": \"E1\",\n      \"time\": \"09:00\",\n      \"role\": \"R-A\",\n      \"action\": \"approve\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    },\n    {\n      \"id\": \"E2\",\n      \"time\": \"09:00\",\n      \"role\": \"R-B\",\n      \"action\": \"withdraw\",\n      \"revision\": 2,\n      \"audience\": \"external\"\n    }\n  ],\n  \"question\": \"May this current revision be distributed externally now? State the next permitted action and any required clarification.\",\n  \"document_id\": \"DOC-J6\"\n}"
    }
  ],
  "run_configuration": {
    "model": "x-ai/grok-4.3",
    "max_tokens": 1024,
    "reasoning": {
      "effort": "low"
    },
    "temperature": 0,
    "response_format": {
      "type": "json_object"
    }
  },
  "execution": {
    "parallel_limit": 4,
    "requests": 24,
    "retries": 0,
    "provider_fallbacks": false,
    "all_contexts_fresh": true
  },
  "evaluation_protocol": {
    "frozen_at_utc": "2026-09-08T17:10:22.629145+00:00",
    "evaluable": "finish_reason stop and a JSON object. Missing/incomplete/refused outputs remain missing.",
    "task_action": "Exact action plus correctly typed external_distribution_allowed boolean.",
    "scope_evidence": "evidence array has unique supplied IDs only and includes all pre-fixed required evidence IDs. This is a strict citation-format criterion, not a complete semantic-quality judgment.",
    "correction_events": "active_event_ids contains exactly the pre-fixed set, no duplicates; order ignored.",
    "clarification": "Exact pre-fixed clarification tag.",
    "explanation": "Agent separately reads each actual answer against frozen facts and rubric; substantive correctness and strict field failures remain separate.",
    "comparison": "Four dimensions per answer; paired and missing results; no causal/general-quality claim.",
    "blinding": "Use frozen blinding map for condition-masked text review. The reviewing agent knows the design; rendering differences may remain recognizable."
  },
  "freeze_record": {
    "frozen_at_utc": "2026-09-08T17:10:22.632146+00:00",
    "source_sha256": [
      {
        "file": "F02/eingefroren/frozen_design.json",
        "sha256": "1afb437480254a18a3a1ebd08624a6338377839c3d964af0d468bebc5522439b"
      },
      {
        "file": "F02/eingefroren/frozen_requests.json",
        "sha256": "83b6fac67419722f1b0ead86984ce9472517d02631819dbc01a725db193d7634"
      },
      {
        "file": "F02/eingefroren/frozen_reference_rubric.json",
        "sha256": "b5cfb9cb17852524af7c285ee09373b1941db3032da3c355fa4484841b364ebb"
      },
      {
        "file": "F02/eingefroren/frozen_evaluation_protocol.json",
        "sha256": "ff8728bb3846b348a7e574a8b44d5f07e2de4749a397ea30cc844e3dc3fc89d3"
      },
      {
        "file": "F02/eingefroren/frozen_run_parameters.json",
        "sha256": "14e3c837d05bf90ca819f0c3390fba160de962482237a594449ba46a94d4c88c"
      }
    ]
  },
  "publication_note": "Die Falltexte und Antwortaufträge sind vollständig enthalten. Transportdaten und Dienst-IDs sind nicht Bestandteil dieser öffentlichen Ausgabe. Die Prüfsummen dokumentieren die lokal vor dem Lauf festgehaltenen Dateien; sie sind kein externer Zeitstempelnachweis."
}