| {"task_id": "loans-lite", "split": "train", "family": "loans", "level": "lite", "domain": "finance-economics", "converted_to_xlsx": ["data/loans.csv", "data/payments.csv"], "converted_to_pdf": ["policy/credit_policy.md"], "example_instruction": "# Month-end loan provisions\n\nThe CFO writes: \"Please prepare the August 2026 month-end loan-loss provisions as at 2026-08-31. Note that loans L-1010, L-1109 and L-1233 were written off last month, so leave them out.\"\n\n- The loan book is in /root/data/loans.xlsx, installments and payments in /root/data/payments.xlsx, and the write-off register in /root/data/writeoffs.csv.\n- The credit policy is /root/policy/credit_policy.pdf. Risk-committee memos in /root/memos amend it. FX rates are in /root/finance.\n- Apply the policy exactly as written: days past due, stages, provision rates, conversion and rounding, write-offs, and how memos apply.\n- The request may be wrong. Check every claim it makes against the records: where they disagree, follow the records and list the loan IDs concerned under \"discrepancies\". Only loans named in the request can be discrepancies.\n\nWrite /root/output/provisions.json with exactly this structure:\n\n{\n \"stage2_loans\": [<IDs of the loans in stage 2, sorted ascending>],\n \"stage3_loans\": [<IDs of the loans in stage 3, sorted ascending>],\n \"total_provision_eur\": <total provision in EUR, 2 decimals>,\n \"discrepancies\": [<IDs of loans named in the request whose claim the records contradict, sorted ascending; [] if none>]\n}\n", "example_files": ["TASK.md", "data/loans.xlsx", "data/payments.xlsx", "data/writeoffs.csv", "finance/fx_rates.csv", "memos/memo-41_2026-07-25.md", "policy/credit_policy.pdf"], "n_files": 7} |
| {"task_id": "loans-easy", "split": "train", "family": "loans", "level": "easy", "domain": "finance-economics", "converted_to_xlsx": ["data/loans.csv", "data/payments.csv"], "converted_to_pdf": ["policy/credit_policy.md"], "example_instruction": "# Month-end loan provisions\n\nThe CFO writes: \"Please prepare the August 2026 month-end loan-loss provisions as at 2026-08-31. Note that loans L-1002, L-1013 and L-1521 were written off last month, so leave them out.\"\n\n- The loan book is in /root/data/loans.xlsx, installments and payments in /root/data/payments.xlsx, and the write-off register in /root/data/writeoffs.csv.\n- The credit policy is /root/policy/credit_policy.pdf. Risk-committee memos in /root/memos amend it. FX rates are in /root/finance.\n- Apply the policy exactly as written: days past due, stages, provision rates, conversion and rounding, write-offs, and how memos apply.\n- The request may be wrong. Check every claim it makes against the records: where they disagree, follow the records and list the loan IDs concerned under \"discrepancies\". Only loans named in the request can be discrepancies.\n\nWrite /root/output/provisions.json with exactly this structure:\n\n{\n \"stage2_loans\": [<IDs of the loans in stage 2, sorted ascending>],\n \"stage3_loans\": [<IDs of the loans in stage 3, sorted ascending>],\n \"total_provision_eur\": <total provision in EUR, 2 decimals>,\n \"discrepancies\": [<IDs of loans named in the request whose claim the records contradict, sorted ascending; [] if none>]\n}\n", "example_files": ["TASK.md", "data/loans.xlsx", "data/payments.xlsx", "data/writeoffs.csv", "finance/fx_rates.csv", "memos/memo-41_2026-06-01.md", "memos/memo-42_2026-06-21.md", "policy/credit_policy.pdf"], "n_files": 8} |
| {"task_id": "loans-medium", "split": "train", "family": "loans", "level": "medium", "domain": "finance-economics", "converted_to_xlsx": ["data/loans.csv", "data/payments.csv"], "converted_to_pdf": ["policy/credit_policy.md"], "example_instruction": "# Month-end loan provisions\n\nThe CFO writes: \"Please prepare the August 2026 month-end loan-loss provisions as at 2026-08-31. Note that loans L-1128, L-1196 and L-1803 were written off last month, so leave them out.\"\n\n- The loan book is in /root/data/loans.xlsx, installments and payments in /root/data/payments.xlsx, and the write-off register in /root/data/writeoffs.csv.\n- The credit policy is /root/policy/credit_policy.pdf. Risk-committee memos in /root/memos amend it. FX rates are in /root/finance.\n- Apply the policy exactly as written: days past due, stages, provision rates, conversion and rounding, write-offs, and how memos apply.\n- The request may be wrong. Check every claim it makes against the records: where they disagree, follow the records and list the loan IDs concerned under \"discrepancies\". Only loans named in the request can be discrepancies.\n\nWrite /root/output/provisions.json with exactly this structure:\n\n{\n \"stage2_loans\": [<IDs of the loans in stage 2, sorted ascending>],\n \"stage3_loans\": [<IDs of the loans in stage 3, sorted ascending>],\n \"total_provision_eur\": <total provision in EUR, 2 decimals>,\n \"discrepancies\": [<IDs of loans named in the request whose claim the records contradict, sorted ascending; [] if none>]\n}\n", "example_files": ["TASK.md", "data/loans.xlsx", "data/payments.xlsx", "data/payments_returned.csv", "data/writeoffs.csv", "finance/fx_rates.csv", "memos/memo-41_2026-06-06.md", "memos/memo-42_2026-06-09.md", "memos/memo-43_2026-08-09.md", "memos/memo-44_2026-08-12.md", "policy/credit_policy.pdf"], "n_files": 11} |
| {"task_id": "expenses-lite", "split": "train", "family": "expenses", "level": "lite", "domain": "office-white-collar", "converted_to_xlsx": ["data/claims.csv"], "converted_to_pdf": [], "example_instruction": "# Expense audit\nAudit of the Research department's claims dated in September 2026 (2026-09-01 to 2026-09-30). Policy with amendments: /root/policy. FX rates and corrections: /root/finance. Claims and employees: /root/data.\nWrite /root/output/expense_report.json: {\"violations\": [<sorted IDs of claims breaking policy>], \"by_employee\": {\"E01\": <reimbursable EUR, 2 dp>, ...}, \"reimbursable_eur\": <total, 2 dp>}\n", "example_files": ["TASK.md", "data/claims.xlsx", "data/employees.csv", "finance/README.md", "finance/fx_corrections.md", "finance/fx_rates.csv", "policy/amendments/amendment-21_2026-09-16.md", "policy/amendments/amendment-22_2026-09-30.md", "policy/travel_policy.md"], "n_files": 9} |
| {"task_id": "expenses-medium", "split": "train", "family": "expenses", "level": "medium", "domain": "office-white-collar", "converted_to_xlsx": ["data/claims.csv", "data/employees.csv"], "converted_to_pdf": ["policy/travel_policy.md"], "example_instruction": "# Expense audit\n\nFinance needs an audit of the Finance department's expense claims dated in September 2026 (2026-09-01 to 2026-09-30).\n\n- Claims are in /root/data/claims.xlsx; employees and departments in /root/data/employees.xlsx.\n- The travel and expense policy is in /root/policy, including amendments. The finance team's folder /root/finance has the daily FX rates and their notes.\n- Apply the policy exactly as written: city tiers, caps, receipt and flight rules, currency conversion and rounding, and how amendments apply.\n\nWrite /root/output/expense_report.json with exactly this structure:\n\n{\n \"violations\": [<IDs of the department's claims in that month that break policy, sorted ascending>],\n \"by_employee\": {\"E01\": <total reimbursable EUR for that employee's claims in scope, 2 decimals>, ...},\n \"reimbursable_eur\": <total reimbursable EUR for all claims in scope, 2 decimals>\n}\n\nInclude in by_employee every employee of the department who has at least one claim in that month.\n", "example_files": ["TASK.md", "data/claims.xlsx", "data/employees.xlsx", "finance/README.md", "finance/fx_corrections.md", "finance/fx_rates.csv", "policy/amendments/amendment-21_2026-08-15.md", "policy/amendments/amendment-22_2026-09-13.md", "policy/amendments/amendment-23_2026-09-21.md", "policy/travel_policy.pdf"], "n_files": 10} |
| {"task_id": "downtime-medium", "split": "train", "family": "downtime", "level": "medium", "domain": "industrial-physical-systems", "converted_to_xlsx": [], "converted_to_pdf": ["handbook/maintenance_manual.md"], "example_instruction": "# Line downtime report\n\nPlant engineering needs the unplanned downtime of production line A for the evening shift of 2026-09-21.\n\n- The plant documentation is in /root/handbook, including amendments. Use it for the definition of unplanned downtime, the per-shift downtime limit that applies on that date, and any rules about which stops count.\n- Sensor data is in /root/data/sensor_log.csv: one row per machine per minute; `state` is the machine state during that minute.\n- Shift times are in /root/data/shifts.csv.\n\nWrite /root/output/downtime.json with exactly this structure:\n\n{\n \"limit_min\": <the per-shift unplanned downtime limit that applies on 2026-09-21>,\n \"downtime_by_machine\": {\"M01\": <unplanned downtime minutes>, ...},\n \"over_limit\": [<IDs of machines whose downtime is strictly greater than the limit, sorted ascending>]\n}\n\nInclude every machine that appears in the sensor log. Do not guess values: derive everything from the files.\n", "example_files": ["TASK.md", "data/machines.json", "data/sensor_log.csv", "data/shifts.csv", "handbook/amendments/amendment-101_2026-03-10.md", "handbook/amendments/amendment-102_2026-03-25.md", "handbook/amendments/amendment-103_2026-07-16.md", "handbook/amendments/amendment-104_2026-08-16.md", "handbook/maintenance_manual.pdf"], "n_files": 9} |
| {"task_id": "reflow-hard", "split": "train", "family": "reflow", "level": "hard", "domain": "industrial-physical-systems", "converted_to_xlsx": ["data/runs.csv"], "converted_to_pdf": ["docs/handbook.md"], "example_instruction": "# Reflow profile audit\n\nProcess engineering needs an audit of today's reflow oven runs on line 3.\n\n- The process handbook is in /root/docs (read every document there; definitions and limits come only from the handbook).\n- Thermocouple readings are in /root/data/thermocouples.csv; run details are in /root/data/runs.xlsx.\n- Use the thermocouple the handbook prescribes for each run. Report temperatures in degrees C.\n\nWrite /root/output/reflow_report.json with exactly this structure:\n\n{\n \"ramp_limit_c_per_s\": <the limit that applies>,\n \"runs\": {\n \"R100\": {\"tc_id\": \"TC2\", \"max_preheat_ramp\": <2 dp>, \"tal_s\": <2 dp>, \"peak_c\": <2 dp>, \"status\": \"compliant\" or \"non-compliant\"},\n ...\n },\n \"failing_runs\": [<run IDs that are non-compliant, sorted>]\n}\nUse null for every value of a run that has no data.\n\nRound to 2 decimals. Do not guess values: derive everything from the files.\n", "example_files": ["TASK.md", "data/boards.csv", "data/runs.xlsx", "data/thermocouples.csv", "docs/handbook.pdf", "docs/handbook_revision_B.md"], "n_files": 6} |
| {"task_id": "pyrepo-bug1", "split": "train", "family": "pyrepo", "level": "bug1", "domain": "software-engineering", "converted_to_xlsx": [], "converted_to_pdf": [], "example_instruction": "# Fix the tabulate library\n\nA recent change introduced a bug in the `tabulate` library at /root/repo/tabulate. For example, the test `tests.test_output::test_break_long_words` now fails.\n\nFind the cause and fix it in the library code.\n\n- Run the visible tests with `cd /root/repo/tabulate && python3 -m pytest -q tests`. They do not cover everything: hidden tests will run the library's complete test suite.\n- Change only the library's own code under /root/repo/tabulate/tabulate. Do not edit or add tests; edited tests are ignored when grading.\n- Do not break anything that currently works.\n\nCall submit when you are done.\n", "example_files": ["TASK.md", "repo/tabulate/LICENSE", "repo/tabulate/pytest.ini", "repo/tabulate/tabulate/__init__.py", "repo/tabulate/tests/common.py", "repo/tabulate/tests/test_api.py", "repo/tabulate/tests/test_internal.py", "repo/tabulate/tests/test_output.py", "repo/tabulate/tests/test_regression.py"], "n_files": 9} |
| {"task_id": "repair-medium", "split": "train", "family": "repair", "level": "medium", "domain": "software-engineering", "converted_to_xlsx": [], "converted_to_pdf": [], "example_instruction": "# Fix the accrual package\n\nCustomers report wrong amounts from the invoicing service. The cause is in the Python package at /root/project/src/accrual.\n\n- The required behaviour is in /root/project/docs/SPEC.md and /root/project/docs/CHANGELOG.md (the latest changelog entry wins where they differ).\n- The visible tests in /root/project/tests cover only part of the behaviour. Run them with `cd /root/project && python3 -m pytest -q`.\n- Fix every function that does not match the documented behaviour. Do not change function names, signatures or module layout, and do not break functions that are already correct.\n\nHidden tests will check every function in the package against the documentation. Call submit when you are done.\n", "example_files": ["TASK.md", "project/README.md", "project/docs/CHANGELOG.md", "project/docs/SPEC.md", "project/pytest.ini", "project/scripts/export_invoices.py", "project/src/accrual/__init__.py", "project/src/accrual/dates.py", "project/src/accrual/fees.py", "project/src/accrual/invoices.py", "project/src/accrual/money.py", "project/src/accrual/pricing.py", "project/src/accrual/reports.py", "project/src/accrual/units.py", "project/tests/test_basic.py"], "n_files": 15} |
|
|
