Program 01 / Coding environments
Code that survives the checks.
Explore repository tasks with a runnable starting state, an explicit output contract, and deterministic checks.
01 / The task
Start with a concrete assignment.
Refactor a small service without changing its public behavior; submit the patch and a structured verification report.
Input materials
A fixed repository revision, setup instructions, representative fixtures, dependency constraints, and the required report schema. State which files may change and which commands establish the baseline.
02 / The workflow
Carry the task through.
- 01
Recreate the starting environment, run the baseline checks, and map the code paths affected by the request.
- 02
Make the smallest coherent change. Preserve interfaces and record any assumptions needed to interpret incomplete instructions.
- 03
Run the agreed checks, inspect the diff, and produce a report connecting each requirement to evidence.
03 / The deliverables
Work you can inspect.
- 01Task workspace
- 02Code patch
- 03Test results
- 04Review notes
04 / The evaluation
Make the criteria explicit.
Check behavior, output structure, and task constraints against a fixed starting revision.
- The workspace starts cleanly and the verification commands can be repeated.
- Required outputs satisfy their schema; failed checks remain visible in the report.
- The patch respects allowed paths, dependencies, and behavior outside the requested change.
Delivery boundary
Acceptance covers the specified fixtures and environment. Broader performance, security, and production compatibility require separately agreed checks; passing the example does not establish them.