Challenges4 000CP pool
ClosedCode

Code Space Workflow

Shape the contributor workspace for code challenges. Each contributor gets a personal kanban and a dedicated branch (or their own repo). They work the full scope in parallel and trigger a single evaluation of their whole delivery once their board is done.

1 participant · own branch each

Why this challenge exists

Code challenges follow the same live-reward philosophy as ML. Contributors self-organize and work in parallel on the full challenge scope, and each one's participation record carries their own workspace.

Who hosts this challenge

MyTwin Lab

The brief

Objective

When a contributor joins, they get a personal kanban board (todo → in progress → done). Tasks are purely organizational and never scored. Their workspace is either their own or a shared repo

Once the board is done and the workspace is ready, the contributor triggers one evaluation of their whole delivery.

Expected result

• The evaluation runs against the code grid

• The reward is a fixed part on the first successful run plus a part scaled by the score, clamped to the remaining pool

• Re-evaluating is safe: a lower score never claws back points, a higher one pays the positive delta

• Closing a challenge only stops new joins and evaluations, because rewards are already paid