Inspectable repositories
Cloneable bundles, a file inventory, and integrity evidence for the exact collection under review.
02Codebases & tasks
Software with history.Tasks with a test.
Repository collections with engineering history, and scoped build or repair tasks with executable checks. Give coding models the context around the code.
Inside the program
Material your
team can use.
A concrete task contract
The starting state, instructions, permitted tools, expected outputs, and environment requirements.
Executable verification
For graded tasks, the checker, control runs, and documented limits of what the checks establish.
A separation plan
Source overlap and train/evaluation separation are considered before assigning tasks to a split.
From brief to production
Build to your
research question.
Choose repository data, graded tasks, or both. Use a small technical review to establish language, environment, task difficulty, and the checks your team needs.
Testing whether a task can be passed by recallRepository inventory and task inventory are different products. Availability, licensing, environment support, and difficulty are confirmed for the proposed release.
Work with Gerra
What should your coding agent be able to build or repair?
Share the task, the material you need, and how you will judge a useful result. We will shape the first review set with you.
Let’s talkteam@gerra.com