environment stringclasses 18
values | case_version stringclasses 18
values | task_id stringlengths 9 39 | task_index int64 1 32 | stream_length int64 16 32 | task_prompt stringlengths 1.54k 6.67k | case_path stringclasses 18
values |
|---|---|---|---|---|---|---|
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T17 | 17 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T18 | 18 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T19 | 19 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T20 | 20 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T21 | 21 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T22 | 22 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T23 | 23 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
k8s_operations | k8s-namespace-migration-evolution-v6 | k8s_operations/T24 | 24 | 24 | {"allowed_tools": ["list_clusters", "list_namespaces", "inspect_release_policy", "publish_deployment", "create_service", "list_worker_pools", "inspect_worker_pool"], "budget": {"limits": [{"resource": "API work units", "allowance": 120}], "charging": ["Cluster and namespace catalogs cost two work units plus the scanned... | cases/k8s_operations |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T01 | 1 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T02 | 2 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T03 | 3 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T04 | 4 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T05 | 5 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T06 | 6 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T07 | 7 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T08 | 8 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T09 | 9 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T10 | 10 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T11 | 11 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T12 | 12 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T13 | 13 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T14 | 14 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T15 | 15 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
medical_appointment | medical-delivered-followups-evolution-v5 | medical_appointment/T16 | 16 | 16 | Create one policy-compliant follow-up appointment for each active request. Keep every appointment linked to its completed source encounter and use a currently eligible slot. Follow-up requests are independent and may be processed in any order. An incomplete request does not block another patient's appointment. Each app... | cases/medical_appointment |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T01 | 1 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T02 | 2 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T03 | 3 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T04 | 4 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T05 | 5 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T06 | 6 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T07 | 7 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T08 | 8 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T09 | 9 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T10 | 10 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T11 | 11 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T12 | 12 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T13 | 13 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T14 | 14 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T15 | 15 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
mes_order_closeout | mes-coherent-time-defaults-evolution-v8 | mes_order_closeout/T16 | 16 | 16 | {"budget": {"charging": ["find_production_orders charges 4 units per bounded page; inspect_order_closeout charges 9 units per aggregate; both find_inventory_lots and find_issuable_inventory_lots charge 4 units per bounded page; inspect_equipment charges 3 units per aggregate.", "Every allowed write call admitted to the... | cases/mes_order_closeout |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T01 | 1 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T02 | 2 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T03 | 3 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T04 | 4 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T05 | 5 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T06 | 6 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T07 | 7 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T08 | 8 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T09 | 9 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T10 | 10 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T11 | 11 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T12 | 12 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T13 | 13 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T14 | 14 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T15 | 15 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
oracle_clinical_one_data_collection | oracle-independent-corrections-evolution-v3 | oracle_clinical_one_data_collection/T16 | 16 | 16 | {"budget": {"charging": ["Context dossier joins cost 5 work units; policy and revision lookups cost 3; successful or failed correction writes cost 2."], "exhaustion": "Further charged business operations are rejected once the allowance is exhausted.", "limits": [{"allowance": 17, "resource": "backend work units"}], "pe... | cases/oracle_clinical_one_data_collection |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T01 | 1 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-d5d48ff7917aaf9477e8", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T02 | 2 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-6efc2a3c7af721e767fd", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T03 | 3 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-c5ca98fb0870d338f51c", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T04 | 4 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-33393f3960879a34c950", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T05 | 5 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-5b196dc5155d5f784c29", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T06 | 6 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-84d4c34706deb7378b18", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T07 | 7 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-dedb88902a60fdfa2f65", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T08 | 8 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-7642a6bbd40a0a3c6f5e", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T09 | 9 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-7cafb30e5d8a62f1f8dd", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T10 | 10 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-e6a966e9f7c72c888797", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T11 | 11 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-a28786c7d975488b76d7", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T12 | 12 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-717cc55ba37a5fd2bc09", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T13 | 13 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-348a1c457c54740a97d9", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T14 | 14 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-32cbd2efede3976c689a", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T15 | 15 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-869e59c6a88fd2deba8d", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T16 | 16 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-4378d1c06c7a288e4d4c", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T17 | 17 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-3d6dcdb803e88df02769", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T18 | 18 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-9fc8b88a400472ef8817", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T19 | 19 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-47f03c6490dfaff21eba", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T20 | 20 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-c03c99ab26211376c190", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T21 | 21 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-1f640c9de8a7302f1000", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T22 | 22 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-3f0242b0e6d10c9c663d", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T23 | 23 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-615e567e11c058e1732f", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T24 | 24 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-3c28eb40efba810c4213", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T25 | 25 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-f68ac223d2c82f905f32", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T26 | 26 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-9b6c62567742fd078373", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T27 | 27 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-840ba8691fc53f45cdb5", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T28 | 28 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-35486452ee05223f27e8", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T29 | 29 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-01d9338c0181647de1c0", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T30 | 30 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-91be7b2ed4a7b67ebccb", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T31 | 31 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-16fd7da8a31e2f478067", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
railway_ticketing_c_04_06_01 | railway-balanced-walk-evolution-v8 | railway_ticketing_c_04_06_01/T32 | 32 | 32 | {"schema": "rescopebench-railway-resource-task/v11", "event_id": "evt-7db4e916894b069252f1", "objective": "Fulfill the listed independent booking requests. Each request_id is a separate instruction to purchase an additional ticket, even if its passenger and journey match an earlier request. Each completed request requi... | cases/railway_ticketing |
redcap | redcap-independent-packets-evolution-v3 | redcap/T01 | 1 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T02 | 2 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T03 | 3 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T04 | 4 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T05 | 5 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T06 | 6 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T07 | 7 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T08 | 8 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T09 | 9 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T10 | 10 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T11 | 11 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
redcap | redcap-independent-packets-evolution-v3 | redcap/T12 | 12 | 16 | {"budget": {"charging": ["A successful bounded listing charges at least one read unit and otherwise one unit per matched row before pagination.", "An exact active-packet get_record_profile projection charges two read units during discovery.", "After a packet has closed, an optional exact profile read is served from the... | cases/redcap |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.