DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make a verified task harder and measure its difficulty with Evo Trace

Derive a harder child task from a verified one, then measure it with fresh solver attempts.

Who it is forA researcher building a difficulty curriculum for coding agents who needs measured difficulty rather than guesses from patch size.

The problemEasy verified tasks saturate quickly, and making a patch longer does not make a task harder.

The outcomeA harder child task with a calibration result based on fresh solver attempts against the default target of two verifier passes in five attempts.

What you need first

  • Existing Claude Code or Codex session history on the local machine
  • Git, and Node.js 22.19+ or 24+ for the DeepSeek Harness app
  • A model provider configured in Harness Settings for review, hardening, calibration, and evolution
  • Docker, only when building or validating executable environments

Steps

  1. Install and launch Evo Trace with curl -LsSf https://raw.githubusercontent.com/jinzijian/EvoTrace/main/install.sh | sh and then evotrace.
  2. Make sure a verified asset exists and Docker is available.
  3. Run /harden 1 to derive and test a harder child task.
  4. Run /calibrate 2 on the child task to measure difficulty with self-play.

Prompt for your agent

Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, run /harden 1 and then /calibrate on the resulting child asset in the DeepSeek Harness app. Report the calibration pass count out of attempts and the added behavior. Verify that the child task adds testable behavior, compatibility, edge cases, or failure constraints rather than only a longer patch.

Caveat. Self-play and evolution send selected task context to the configured model, so only run them on material you are allowed to send.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page