Step 01
Enter the environment
Each challenge defines inputs, constraints, expected behavior, and evaluation criteria.
The learning loop
Versalist is built around environment, action, and reward.
That loop is what trains strong systems, and it is also the cleanest way to train strong engineers. Public pages stay open. Authentication starts when you want to save work, run protected resources, or track progress.
Why sign in exists
Episode history is useful only when runs persist across sessions.
Protected challenge data and API credentials need scoped access.
Your eval record, certificates, and workspace recommendations depend on stable identity.
Public before account
You can browse challenges, tools, docs, and guides without creating an account. Sign-in begins when the product needs to remember or provision something for you.
The three-part loop
A developer should be able to understand the product model in one scan.
Step 02
Run the system
Run a selected skill and model against the challenge cases. Trace capture can record bounded call metadata when it is enabled.
Step 03
Collect the reward signal
Evaluations score across weighted dimensions so you can see what worked, what broke, and what should change in the next iteration.
What happens after the first run
The value of the platform shows up in the second and third attempt, not just the first completion.
Inspect available metadata
When trace capture is enabled, review logical agent and judge calls. Tool and sandbox events are not available.
Adjust the setup
Change prompts, model selection, decomposition, or validation where the evaluation shows weakness.
Re-run with signal
Compare scores and artifacts against earlier attempts so progress is measurable rather than intuitive.
Ready to start
Jump into public surfaces now, then authenticate when you need persistence or protected resources.