The width of the band is the test
The task does not ask for one number: it asks for a floor, a ceiling and where the spread comes from. The band has to follow from the disagreements in the material.
YKCX-FIN-MEMO-939 · Asset-side forecast · capex and depreciation · flip point
The sell-side material covers only the asset side. From an 18-worksheet financial model, reconcile total new long-lived asset spend, put a floor and a ceiling on the closing balance and explain why the band is that wide, take a stance, and compute what would flip it.
The task does not ask for one number: it asks for a floor, a ceiling and where the spread comes from. The band has to follow from the disagreements in the material.
After taking an adopt / adopt-with-reservations / reject stance, state the asset-consumption level at which the stance flips, or why it does not flip.
Beyond the workbook and the structured JSON, the memo must tell the client in one sentence which element matters most to the conclusion, and why.
Three models answered under the same criteria for a mean of 0.4590, all below 0.52. The bar here is not arithmetic but explaining where the width of the band comes from.
An excerpt of the instruction the agent actually receives, showing the task setup and constraints.
You are an investment adviser in a private bank's wealth management department. A client has received sell-side forecast material on a clinic chain that is opening new sites and wants an independent view on the asset-side forecast before adjusting the position.
NOTEEnglish translation of the original Chinese instruction; the block structure and field definitions of the three deliverables are omitted.
Everything visible inside the agent container, with statistics generated from the task package. Original files ship with the full sample package.
| File | Type | Size | Bytes |
|---|---|---|---|
| 中弘智造_底稿.xlsxFinancial forecast and valuation model: fixed assets and long-term prepaid expense forecasts, financial statements, source data, assumptions (18 worksheets) | xlsx | 18 sheets | 357 KB |
Full criteria text, weights and reference answers ship with the complete data package.
Trajectory statistics from frontier models in real agent harnesses. One turn is one model call; the context curve shows how state accumulates over a long-horizon task.
| Model | Agent turns | Tool calls | Cumulative prompt tokens | Peak context | Time | Result |
|---|---|---|---|---|---|---|
| Claude Opus 4.8Claude Code · Harbor | 18 | 1.53M | 107K | — | Completed | |
| GPT-5.6-solCodex · Harbor | 27 | 1.41M | 68K | — | Completed | |
| Qwen3.8-MaxClaude Code · Harbor | 43 | 2.53M | 122K | — | Completed |
| Task ID | YKCX-FIN-MEMO-939 |
|---|---|
| Task format | Harbor task.toml · schema 1.4 |
| Package version | 1.0.0 |
| Agent time limit | 3 h |
| Verifier time limit | 5 h |
| Agent container | 2 vCPU · 8 GB memory · 30 GB storage |
| Network | Only for agent harness installation |
| Tool set | filesystem · shell · python |
| Scoring isolation | Separate verifier containerJudge credentials are injected only into the verifier and are invisible to the agent |
| Instruction length | 2,307 characters |
| Difficulty | A3 (three-model mean 0.4590) |
| Reference solution | oracle reward 1.000 |
| Workpaper size | 18 worksheets · 2008–2012 history and 2013E–2017E forecast |
Leave your details and we will send the full sample package for this task (instruction, attachments, verifier and reference trajectories) and walk you through volume and customisation for similar tasks.